chore(deps): bump utoipa from 5.5.0 to 6.0.0 - #2413
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [utoipa](https://github.com/juhaku/utoipa) from 5.5.0 to 6.0.0. - [Release notes](https://github.com/juhaku/utoipa/releases) - [Changelog](https://github.com/juhaku/utoipa/blob/master/utoipa-rapidoc/CHANGELOG.md) - [Commits](juhaku/utoipa@utoipa-5.5.0...utoipa-6.0.0) --- updated-dependencies: - dependency-name: utoipa dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
…ether (#2429) Combines #2413 and #2414, which could not land independently: utoipa-swagger-ui 9.0.2 requires utoipa ^5, and 10.0.1 requires utoipa ^6.0.0, so the two must bump together or the build fails with two incompatible utoipa crate instances (E0308). - Bumps velesdb-core's utoipa 5.3.0 -> 6.0.0 and velesdb-server's utoipa/utoipa-swagger-ui 5.3.0/9 -> 6.0.0/10 together. - Regenerates docs/openapi.{json,yaml}: utoipa 6.0.0 reorders the null variant in Option<T>'s oneOf schema (cosmetic, same semantics). - Review-fix: marks the bump BREAKING in CHANGELOG.md for downstream crates enabling the openapi feature with their own utoipa 5 dependency, and adds swagger_ui_tests.rs covering the swagger-ui route (previously unreachable from any test, since the version bump changed the asset-embedding mechanism the bundle uses).
|
Superseded by #2429, which combines both bumps since they can't land independently (utoipa-swagger-ui 9.0.2 needs utoipa ^5, 10.0.1 needs utoipa ^6.0.0). |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
…ether Reauthored and combined from dependabot PRs cyberlife-coder#2413 (utoipa) and cyberlife-coder#2414 (utoipa-swagger-ui) -- bot commits rejected by the AI/bot-attribution guard, and the two bumps cannot land independently: utoipa-swagger-ui 9.0.2 depends on utoipa ^5, so bumping utoipa alone to 6.0.0 while utoipa-swagger-ui stays at 9.0.2 pulls in two incompatible instances of the utoipa crate and fails to compile (E0308, "two different versions of crate utoipa are being used", crates/velesdb-server/src/main.rs:189). utoipa-swagger-ui 10.0.1 requires utoipa ^6.0.0, so the two must bump together. Also regenerated docs/openapi.{json,yaml}: utoipa 6.0.0 changed the variant order it emits for an Option<T> field's oneOf schema (the null variant now comes after the $ref instead of before it) -- same schema, same semantics, just reordered, confirmed by diff (8-24 lines, all reorderings of the same two variants). Verified: cargo check --workspace --all-targets --all-features --exclude velesdb-python (the compat-matrix job's exact command) is clean on both platforms-equivalent build; fmt --check and clippy pedantic clean on velesdb-server and velesdb-core; velesdb-server's full test suite (352 tests) passes; cargo deny check advisories licenses bans sources is clean.
Bumps utoipa from 5.5.0 to 6.0.0.
Release notes
Sourced from utoipa's releases.
... (truncated)
Changelog
Sourced from utoipa's changelog.
... (truncated)
Commits
baa4d04Remove support for expression ignore inToSchemaandIntoParams(#1619)14e2a90Update next release versions (#1618)69af040Re-enable actix auto_into_responses Result test (#1603)0f601fefeature: support extensions in utoipa::ToSchema named structs (#1593)fbe6639Upgrade utoipa-gen to syn 3 (#1597)1436f78Bump base64 from 22.1 to 23.1 (#1595)0a5951bchore: Update CHANGELOG.md (#1596)5db2ccbRefactor documentation in lib.rs (#1581)e8a26bbRecursively discover flattened fields in maps (#1582)b66879afeat(gen): support item_schema attribute for streaming/SSE response types (#1...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)